Add release operator checklist - #425
Open
Alek99 wants to merge 3 commits into
Open
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe PR adds an ordered release-operator checklist. It covers preparation, artifact validation, publication, clean-install checks, release media, recovery procedures, and final sign-off. Contributor and production-readiness documents reference the checklist. ChangesRelease process
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Merging this PR will not alter performance
Comparing 
Footnotes
|
Alek99
force-pushed
the
agent/add-release-checklist
branch
from
August 7, 2026 18:32
9577020 to
48c934b
Compare
Alek99
marked this pull request as ready for review
August 7, 2026 18:32
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@spec/process/release-checklist.md`:
- Around line 84-91: Update the coreless import check in the release checklist
so CI verifies that importing xy and reflex_xy does not eagerly load NumPy,
Reflex, or the native core, while retaining the assertion that requesting
compute raises the documented native-core ImportError; alternatively, narrow the
checklist requirement to match only the behavior the CI step actually tests.
- Around line 76-80: Update both local sdist smoke instructions in the release
checklist to create a fresh isolated environment using the CI uv venv pattern,
then run the smoke interpreter from outside the repository so checkout files
cannot shadow the installed distribution; retain the existing XY_REQUIRE_CARGO=1
installation behavior.
- Around line 162-171: Update the temporary-directory initialization in the
release smoke-test commands to use the portable ${TMPDIR:-/tmp} base path
instead of the macOS-specific /private/tmp path, while preserving the existing
unique directory suffix and subsequent UV_CACHE_DIR and virtual-environment
usage.
- Around line 67-74: Update the release workflow’s Rust installation
configuration to use a genuine SHA checksum for the release-tool Rust version
instead of the current tag-only value, while preserving the action’s commit-SHA
pin. If a verified checksum cannot be provided, remove the checksum field and
document the Rust version used by the release workflow.
- Around line 78-80: Update both local sdist installation examples in the
release checklist to install numpy, anywidget, and reflex>=0.9.6 alongside the
archive, matching the CI setup before running reflex_xy smoke checks. Preserve
the existing XY_REQUIRE_CARGO=1 variant and apply the dependency additions to
both commands.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 567c0df6-342e-4844-94f4-0acd7771afa4
📒 Files selected for processing (3)
CONTRIBUTING.mdspec/process/production-readiness.mdspec/process/release-checklist.md
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
All reported issues were addressed across 3 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
xyand the bundledreflex_xyintegrationWhy
The production-readiness spec captures release invariants, but maintainers also need an end-to-end operating procedure. This records the lessons from the 0.0.5 release, especially PyPI immutability, Rust/native verification, optional Reflex boundaries, testing the published package from a clean environment, and preparing accurate release media without publishing before approval.
Impact
Documentation only. Release maintainers get a repeatable release and media-production path without changes to package or workflow behavior.
Validation
uv run --with pre-commit pre-commit run --all-filesuv run ruff check .uv run ruff format --check ..venv/bin/python scripts/verify_local.py --only examples— 9 passed, 2 skippedgit diff --cached --checkSummary by CodeRabbit